Managing Heterogeneous Product Features Using a Unified License Manager

ABSTRACT

An information handling system includes a device, a controller, and a license manager subsystem. The controller is configured to determine whether the device has a license assigned and to communicate with the device pursuant to a uniform protocol. The communications include issuing a command to the device to provide an identification and a command to the device to activate itself.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.13/627,569, entitled “Managing Heterogeneous Product Features Using aUnified License Manager,” filed on Sep. 26, 2012, the disclosure ofwhich is hereby expressly incorporated by reference in its entirety.

FIELD OF THE DISCLOSURE

This disclosure generally relates to information handling systems, andmore particularly relates to a system and method for managingheterogeneous product features using a unified license manager.

BACKGROUND

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option is an information handling system. An information handlingsystem generally processes, compiles, stores, and/or communicatesinformation or data for business, personal, or other purposes. Becausetechnology and information handling needs and requirements can varybetween different applications, information handling systems can alsovary regarding what information is handled, how the information ishandled, how much information is processed, stored, or communicated, andhow quickly and efficiently the information can be processed, stored, orcommunicated. The variations in information handling systems allow forinformation handling systems to be general or configured for a specificuser or specific use such as financial transaction processing, airlinereservations, enterprise data storage, or global communications. Inaddition, information handling systems can include a variety of hardwareand software components that can be configured to process, store, andcommunicate information and can include one or more computer systems,data storage systems, and networking systems.

An information handling system, such as a server, can include a networkinterface card, a host bus adaptor, a redundant array of independentdisks, a controller, and the like. Each of these components may have adifferent manufacturer that can require a user of the server to acquirea license before using the component.

BRIEF DESCRIPTION OF THE DRAWINGS

It will be appreciated that for simplicity and clarity of illustration,elements illustrated in the Figures have not necessarily been drawn toscale. For example, the dimensions of some of the elements areexaggerated relative to other elements. Embodiments incorporatingteachings of the present disclosure are shown and described with respectto the drawings presented herein, in which:

FIG. 1 is a block diagram of a licensing system for an informationhandling system according to an embodiment of the present disclosure;

FIG. 2 is another block diagram of a licensing system for an informationhandling system according to an embodiment of the present disclosure;

FIGS. 3 and 4 are a flow diagram of a method for assigning a license tothe information handling system according to an embodiment of thepresent disclosure; and

FIG. 5 is a block diagram of a general information handling systemaccording to an embodiment of the present disclosure.

The use of the same reference symbols in different drawings indicatessimilar or identical items.

DETAILED DESCRIPTION OF DRAWINGS

The following description in combination with the Figures is provided toassist in understanding the teachings disclosed herein. The followingdiscussion will focus on specific implementations and embodiments of theteachings. This focus is provided to assist in describing the teachingsand should not be interpreted as a limitation on the scope orapplicability of the teachings. However, other teachings can certainlybe utilized in this application.

FIG. 1 illustrates a block diagram of a licensing system 100 for aninformation handling system. For purposes of this disclosure, theinformation handling system may include any instrumentality or aggregateof instrumentalities operable to compute, classify, process, transmit,receive, retrieve, originate, switch, store, display, manifest, detect,record, reproduce, handle, or utilize any form of information,intelligence, or data for business, scientific, control, entertainment,or other purposes. For example, an information handling system may be apersonal computer, a PDA, a consumer electronic device, a network serveror storage device, a switch router or other network communicationdevice, or any other suitable device and may vary in size, shape,performance, functionality, and price. The information handling systemmay include memory, one or more processing resources such as a centralprocessing unit (CPU) or hardware or software control logic. Additionalcomponents of the information handling system may include one or morestorage devices, one or more communications ports for communicating withexternal devices as well as various input and output (I/O) devices, suchas a keyboard, a mouse, and a video display. The information handlingsystem may also include one or more buses operable to transmitcommunications between the various hardware components.

The licensing system 100 includes a server 102 that communicates with alicense server 104 via a network 106. The server 102 includes components108, 110, and 112, a controller 114, and a local interface card 118. Thecontroller 114 is in communication with the components 108, 110, and112, with the local interface card 118, and with a memory 120. Thememory 120 can be external to the server 102, or can be located withinthe server.

The local interface card 118 can communicate with a local display 122and with a local keyboard 124. The local interface card 118 can be anintegrated keyboard, video, and mouse (iKVM) interface card that canprovide a local user with access to each of the components 108, 110, and112. The controller 114 includes license manager 116 and daemon 126. Thecontroller 114 can be any type of controller, such as an integrated DellRemote Access Controller (iDRAC), which is an interface card that canprovide out-of-band management of the server 102. In some embodiments,controller 114 may be a baseboard management controller (BMC), which isanother interface card that can provide out-of-band management of theserver 102. The controller 114 can have a processor, a memory, abattery, a network connection, and access to a server chassis bus. Thecontroller 114 can provide different functions for the server 102 suchas power management, virtual media access, and remote consolecapabilities. A local user can utilize the local interface card 118, thelocal display 122, and the keyboard 124 to communicate with thecontroller 114 to access, configure, or assign a license to one of thecomponents 108, 110, and 112, and the controller 114.

The components 108, 110, and 112 in the server 102 may consist ofconstituent elements of server 102, and may include hardware and othersubsystems. Some examples of components include embedded devices,modules providing systems management features, modules providing basicinput/output system (BIOS) functionality, original equipmentmanufacturer (OEM) features, OEM branding, and modules providingPeripheral Component Interconnect-Express (PCIe) functionality. Separatevendors of hardware components may each require a user to receive alicense to use the component.

When the server 102 is turned on, the license manager subsystem 116 cancommunicate with daemon process 126 to detect the components in theserver. The license manager subsystem 116 can also determine whether anyof the components 108, 110, and 112 require activation pursuant to alicense. If so, the license manager subsystem 116 may communicate withthe component over a uniform, device independent protocol to activatethe component pursuant to a license. The uniform protocol may consist ofa language for communications about licensing between a license managersubsystem and a component of an information handling system. Thelanguage may be capable of use by multiple devices of different types.It may also be transport and wire independent. In some embodiments, thelanguage may consist of a series of requests and responses. In furtherembodiments, pursuant to the uniform protocol, the license managersubsystem 116 may send to the component a request for identification andthe component may send a response pursuant to the uniform protocol. Theresponse may provide a unique identification (ID) for the component,such as a peripheral component interconnect (PCI) ID string. In someembodiments, the response may also provide a device type andmanufacturer.

The license manager subsystem 116 may then check its list of licensesagainst the ID of the component. It may verify that it holds a licensefor the component with the ID. In some embodiments, the license managersubsystem 116 may also verify that the license is for the device typeand manufacturer of the component. Alternatively, the license managersubsystem 116 may determine that it does not have a license covering thecomponent, either because it does not have a license for the type ofcomponent or because it does not have a license for the particular ID.For each component lacking a license and requiring activation pursuantto a license, the license manager subsystem 116 can request from thelicense server 104 a license for the component and send to the licenseserver 104 the unique ID for the component.

The license server 104 includes a license key generator (LKG) 128 thatcan generate the license for a specific component based on the unique IDof the component. For example, the LKG 128 can determine whether theunique ID of a component is a proper unique ID. If the unique ID isproper, the LKG 128 can generate the license, and can sign the licensewith a signature. The signature can be an encrypted signature in anextensible markup language (XML) format, or the like. The license server104 can also include the unique ID of the component within the license,such that the unique ID of the license can be matched with a unique IDof a component. In some embodiments, the license server 104 may alsoinclude the manufacturer and device type in the license.

For some components, the license for a component may delineate aspecific list of features of the component to be activated by thelicense. The LKG 128 can also include other restrictions on the licensebased on licensing requirements of the manufacturer of the component.The other restrictions can be that the license is bound to a specificplatform, that the license is bound to a service tag or to the uniqueID, that the license has a time constraint, or the like. Binding thelicense to a specific platform can cause the license to be valid onlyfor a specific system ID, such as an ID associated with the server 102.Binding the license to a specific platform can also cause the license tobe valid only for a specific platform generation, such as a specificoperating system generation. Binding the license to a service tag orunique ID can cause the license to be valid only for a component thathas a service tag or unique ID that matches the unique ID of thelicense. The time constraint for the license can limit the license to aspecific amount of time, indicate a start date and/or an end date of thelicense, indicate that the license is valid during an evaluation period,or the like. In some embodiments, the license may also include apassword, passphrase, or other security token to be passed from thelicense manager subsystem 116 to the component. In further embodiments,the password, passphrase, or other security token may be encoded in thelicense so that it is not readable by a human being. In a fewembodiments, LKG 128 may encode details of the license pursuant to anestablished protocol, in order that license manager 116 is able to parsethe license to extract feature information without the need for specificinstructions. LKG 128 may, for example, generate the license accordingto a form of XML generally used for licenses.

The license server 104 can send the license to the license managersubsystem 116 with the license being embedded in an email, via a webportal interface, via a license management tool, or the like. When thelicense manager subsystem 116 has received the license, the licensemanager subsystem can store the license in a local storage medium, suchas the memory 120.

Once the license manager subsystem 116 has a license for a componentavailable, either because it matched an already-held license with thecomponent or because it ordered a new license and received it from thelicense server 104, the license manager subsystem 116 may activate thecomponent based upon the license. In case there are restrictions on theuse of the component, before activating the component the licensemanager subsystem 116 may parse the license to determine whether theoperation of the component complies with the terms of the restrictions.If for example the licensing requires a certain operating system, thelicense manager subsystem 116 may determine if the component isoperating under control of that operating system. If the restrictionsare met, the license manager subsystem 116 may activate the component.Otherwise, the license manager subsystem 116 may refrain from activatingthe component under the license.

To activate a component, the license manager subsystem 116 may issue afeature enablement command to the component pursuant to the uniformprotocol. The uniform protocol may provide that data about features tobe enabled is passed with the command. In some embodiments, the data maybe placed in a command buffer to be read by the component upon receiptof the command.

In many embodiments, the license manager subsystem 116 may transformdata contained in the license into a form suitable for passing to thecomponent. If the license contains a list of features to be enabled, forinstance, the license manager subsystem 116 may abstract the set offeatures into a binary representation by using bitmaps. Each bit of thebitmap may represent one individual licensable feature. For example, forthe licensing of an iDRAC, bit 0 may control enabling a License GUI andbit 1 may control a command-line interface (CLI). In another example,for licensing a network interface card (NIC), bit 0 could control FibreChannel over Ethernet (FCoE) functionality and bit 1 could control SmallComputer Interface over Internet (iSCSI). Both component firmware andthe license manager subsystem 116 may be aware of the bit definitions,and the bit definitions can be vendor independent. In other embodiments,however, the license sent from the LKG 128 to the license managersubsystem 116 may have already encoded the feature set as a bitmap. Inaddition, if the license contains an encoded password, passphrase, orother security token, the license manager subsystem 116 may decode itbefore passing it to the component.

In further embodiments, the license manager subsystem 116 may pass thefeatures bitmap to the component in the command buffer. The componentmay read the bitmap and activate the indicated features. In someembodiments, the activation step may also require the license managersubsystem 116 to pass to the component a password or other securitytoken to indicate that the license manager subsystem 116 has theauthority to activate the component. In some embodiments, a processother than a daemon process may detect the addition of components to aninformation handling system. The process may, for example, detectcomponents only upon start-up or reboot.

Embodiments of FIG. 1 may simplify the process of activating a device orother component of an information handling system that requires alicense for operation. The embodiments may enable the activation ofdevices added to the information handling system pursuant to a uniformprocedure. The procedure may be completely or largely automatic.Further, in embodiments of FIG. 1, aspects of the license may betransparent to a user; that is, the user may parse the XML of thelicense to understand aspects of the license, such as an identificationof the device under license and the list of features to be enabled.Without the use of a uniform procedure, a system administrator may berequired to undergo different procedures for different manufacturers.For some devices, the procedure may require an administrator to manuallyenter a licensing code as part of the licensing protocol, such asentering the code into an option read-only memory (ROM) or duringstart-up in the disk operating system (DOS). Further, the license codemay be an arbitrary string of characters that does not conveyinformation to a system administrator about operation of the license.

FIG. 2 shows the components of a system 200 to manage licenses forcomponents of a computing device. The managing system 200 includesUnified Server Configurator (USC)/Human Interface Infrastructure (HII)202, consoles/applications 206, host interface 220, unified licensemanager 266, and components 258, 260, 262, and 264.

Unified license manager 266 includes license protocol layer 268, NetworkController Sideband Interface (NC-SI) 270, Management ComponentTransport Protocol (MCTP) 274, Reduced Media Independent Interface(RMII) 272, Inter-Integrated Circuit (I²C) 272, I²C 274, and PCIe 278.Unified license manager 266 may manage licenses for components of aninformation handling system such as a server. It may detect componentsin the information handling system, determine if they require licenses,communicate with them to obtain information used in obtaining licenses,request the licenses, activate the components, deactivate and remove thelicenses, and communicate information about the licenses to managementsystems. In some embodiments, unified license manager 266 may be thelicense manager subsystem 116 of the controller 114 of FIG. 1.

License protocol layer 268 may provide for carrying out licensingtransactions under a uniform protocol. The transactions may includeobtaining an identification of a component, activating the component,removing a license, and requesting a unique identification from acomponent. Unified license manager 266 may operate under a variety ofmanagement software tools and under a variety of bus connections tocomponents of an information handling system. In the embodiment of FIG.2, unified license manager 266 may operate under both NC-SI, in NC-SIlayer 270, and MCTP, in MCTP layer 274. MCTP is a media-independentprotocol for intercommunication among intelligent devices within theplatform management subsystem of a managed computer system. NC-SI is anelectrical interface and protocol defined by the Distributed ManagementTask Force that may enable the connection of a baseboard managementcontroller to a network interface controller in server computer systemsfor the purpose of enabling out-of-band remote manageability.

NC-SI layer 270 communicates with component 258 over an RMII busprotocol. An MII bus (standardized by IEEE 802.3u) may connect differenttypes of physical transceivers to Media Access Controllers (MAC). Thus,any MAC may be used with any transceiver, independent of the networksignal transmission media.

MCTP layer 274 communicates with components 260, 262, and 264 both overI²C and PCIe buses through I²C layer 275 and PCIe layers 278respectively. I²C is a multi-master, two-wire serial bus. It may be usedto attach peripherals to a motherboard. In other embodiments, unifiedlicense manager 266 may operate under other management protocols orthrough other bus methods of communication.

In some embodiments, unified license manager 266 may communicate withthe components 258, 260, 262, and 264 under a uniform,device-independent, management-protocol-independent, wire independentcommunications protocol. The communications protocol may provide for theunified license manager 266 to issue such commands as Request DeviceInformation, Feature Enablement, Revoke License, and Assign UniqueLicense Device ID to components connected to an information handlingsystem. The Request Device Information command may request informationabout a component, such as an identification, a type, or a manufacturer.The Feature Enablement command may instruct the component to activateitself. The Revoke License command may inform the component that thelicense has been revoked, and that the component is to cease operations.The Assign Unique License Device ID may request a unique identificationfrom the component for use in a license. The commands may be embedded ascommands in the management protocols. In some embodiments, the licenseprotocol payload over NC-SI may be carried in OEM command (0x50) andresponse (0xD0). For MCTP, a license command may be carried withinmessage type 0x7E, with the “Application Type” byte set to 0x01 for alicensing message.

Host interface 220 may provide an interface between unified licensemanager 266 and USC/HII 202, and between unified license manager 266 andconsoles/applications 206. USC/HII 202 and consoles/applications 206 areinterfaces for system management and may be used to configure thecomponents that have been activated by unified license manager 266.USC/HII 202 may provide an embedded configuration utility that mayreside on an embedded flash memory card. It may be launched during theboot sequence, and may function in a pre-operating system environment.USC/HII 202 may enable systems and storage management tasks from anembedded environment throughout the life cycle of a system.Consoles/applications 206 are a console and software to enable a systemadministrator to control an information-handling system. USC/HII 202 andConsoles/applications 206 include license protocol layers 204 and 208,respectively. The license protocol layers handle licensing details, suchas which components have been licensed.

Components 258, 260, 262, and 264 are connected to unified licensemanager 266 through buses RMII, I²C, and PCIe. Each component has asoftware layer for the wire communications, layers RMII 226, I²C 234,and I²C 242, and PCIe 250 respectively; layers for communicatingaccording to the management protocols, layers NC-SI 228, MCTP 236, MCTP244, and MCTP 252 respectively; license protocol layers 230, 238, 246,and 254 respectively; and firmware layers, Local Area Network (LAN) on amotherboard (LOM) firmware 232, NIC firmware 240, PowerEdge™ redundantarray of independent disks (RAID) Controller (PERC) firmware 242, andconverged network adapter (CNA) firmware 256, respectively. PowerEdge™is a proprietary Dell server.

License protocol layers 230, 238, 246, and 254 implement uniformprotocols for communicating with unified license manager 266 concerninglicensing operations. The license protocol layers may enable components258, 260, 262, and 264 to interpret and respond to licensing commandssuch as those described above. In some embodiments, to be compliant withthe protocols, the license protocol layers of unified license manager266 and components 258, 260, 262, and 264 are required to implementcertain licensing commands. The implementation of other commands may beoptional for compliance. In further embodiments, the Assign UniqueLicense Device ID may be optional and the other commands may bemandatory.

Firmware 232, 240, 248, and 256 may include code contained innon-volatile memory, such as flash memory, for integrating a componentwith an operating system. In some embodiments, the firmware may containdata to be used in the licensing process, such as a uniqueidentification number for the component, a password or other securitytoken for the component, or a license key or a license number. In someembodiments, the data must be matched with data supplied to thecomponent during the licensing process before the component can beactivated. In addition, when a bitmap or other representation offeatures to be activated is passed to the component, the firmware may beable to parse the bitmap or other representation, determine whichfeatures are to be activated, and activate those features.

In the embodiment of FIG. 2, component 258 may be a LOM, and LOMfirmware 232 may support the LOM. Component 260 may be a networkinterface card, and NIC firmware 240 may support the NIC. Component 262may be RAID controller and PERC firmware 248 may support the RAIDcontroller. Component 264 may be a CNA, a computer input/output devicethat combines the functionality of a host bus adapter with a networkinterface controller. A single card may provide access to both a storagearea network and a general-purpose computer network. CNA firmware 256may support the CNA 264.

In FIG. 2, components 258, 260, 262, and 264 are connected to aninformation-handling system through buses RMII, I²C, and PCIe andoperate under management protocols NC-SI and MCTP. In other embodiments,components may be connected through other wire or bus methods ofcommunication and may operate under other management protocols.

FIGS. 3 and 4 illustrate a method 300 for managing licenses forcomponents of an information handling system, such as a server. At block302, a daemon process of the information handling system detects acomponent, such as when a server is turned on or a component is added tothe server. At block 304, a determination is made whether the componentrequires a license for activation. If the component does not require alicense, either because it has already been activated pursuant to alicense or because the component does not require a license to operate,the method returns to block 302, to examine the next component. If thecomponent requires a license to be activated, a license managersubsystem may issue to the component a request for a uniqueidentification (ID) for the component at block 306. The license managersubsystem may extract the ID from the response to the request. Theunique ID can be a peripheral component interconnect (PCI) ID string. Insome embodiments, a unique ID is unnecessary. In some embodiments, thelicense manager subsystem may have already obtained a unique ID for thecomponent, and it is unnecessary to request the ID.

At block 308, a determination is made whether a license is assigned tothe component. The license manager subsystem may check if a license forthe component is contained in a list of licenses. The license managersubsystem may maintain the list in non-volatile storage, or the list maybe stored in another component of the information handling system, suchas USC/HII or firmware, and the license manager subsystem may ask theother component about the status of a license for the component. In someembodiments, the licenses are stored by type of component and by uniqueID. The license manager subsystem may check if there is a license forthe type of component; and if so, for the component with that unique ID.

If a license was already obtained for the component, the flow proceedsto block 402 of FIG. 4. Otherwise, the unique ID for the component isreturned to the license manager subsystem and the unique ID for thecomponent is sent from the license manager subsystem to a license serverto request the license for the components at block 310. The license forthe component is generated by a license key generator based on theunique ID of the specific component at block 312. The license can be inan extensible markup language (XML) format, or the like. At block 314,the license is signed with an encrypted signature. The unique ID of thecomponent is included within the license at block 316.

At block 318, restrictions on the license are included in the licensebased on licensing requirements of a manufacturer of the component. Therestrictions can be that the license is bound to a specific platform,that the license is bound to a service tag or the unique ID, that thelicense has a time constraint, or the like. Binding the license to aspecific platform can cause the license to be valid only for a specificsystem ID, such as an ID associated with the server. Binding the licenseto a specific platform can also cause the license to be valid only for aspecific platform generation, such as a specific operating systemgeneration. Binding the license to a service tag or unique ID can causethe license to be valid only for a component that has service tag orunique ID that matches the unique ID of the license. The time constraintfor the license can limit the license for a specific amount of time,indicate a start date and/or and end date of the license, indicate thatthe license is valid during an evaluation period, or the like.

At block 320, a data structure delineating a specific list of featuresof the component to be activated by the license is included in thelicense. In some embodiments, the license may abstract the feature setsinto a binary representation by using bitmaps. Each bit of the bitmapmay represent one individual licensable feature. A value of 1 is aposition may indicate that a feature is to be activated, and a value of0 may indicate that the feature is not to be activated. Both componentfirmware and the license manager subsystem 116 may be aware of the bitdefinitions, and the bit definitions can be vendor independent. In otherembodiments, the license manager subsystem may parse the license toobtain a list of features and may represent the list with a bitmap. Instill other embodiments, another representation of features may be usedor a representation may be unnecessary because activation does notinvolve specification of a list of features.

At block 322, a password, passphrase, or other security token isincluded in the license. The security token is to be passed by thelicense manager subsystem to the component as part of activation of thecomponent in accordance with the license. The use of a security token tobe passed to the component is optional. In some embodiments, a securitytoken for activation of the component is not included in the license. Atblock 324, the license is sent to the license manager subsystem. Thelicense can be sent via email, via a web portal interface, via a licensemanagement tool, or the like. The license is stored in a local storagemedium in response to the license manager subsystem receiving thelicense at block 326. Flow now proceeds to block 402 of FIG. 4.

At block 402, the encrypted signature of the license is verified. Atblock 404, the license is parsed for identification of the component towhich it applies and the list of features to be activated. In someembodiments, the license may also be parsed to obtain a password orother security token to pass to the component for activation. Thelicense may consist of an XML document and parsing the license mayrequire parsing the XML. The list of features may then be represented asa bitmap. For example, the following may illustrate a small portion ofan XML license that describes the features of a component to beactivated:

<lns:LicenseData> .... <lns:Feature lns:ID=“1” lns:Description=“LicenseManager Interface” lns:Enabled=“true”/>  <lns:Feature lns:ID=“2”lns:Description=“RACADM CLI” lns:Enabled=“true”/>  <lns:Featurelns:ID=“3” lns:Description=“WSMAN protocol stack” lns:Enabled=“true”/> <lns:Feature lns:ID=“4” lns:Description=“SNMP GET/MIB and Alerts”lns:Enabled=“true”/>  <lns:Feature lns:ID=“5”lns:Description=“Auto-Discovery” lns:Enabled=“true”/>  <lns:Featurelns:ID=“6” lns:Description=“USC firmware update (Pre-OS)”lns:Enabled=“true”/>  <lns:Feature lns:ID=“7” lns:Description=“Firmwareupdate In-band Customer Tier  1 OS” lns:Enabled=“true”/>  <lns:Featurelns:ID=“4” lns:Description=“USC operating system deployment with drivermedia” lns:Enabled=“true”/> <lns:Feature lns:ID=“9” lns:Description=“USCdevice configuration” lns:Enabled=“true”/> ... </lns:LicenseData>

This list of features may be bit mapped into 32 bits and transmitted tothe component to be activated. An enabled feature may be represented asa 1 and a feature not enabled may be represented as a zero. In the aboveexample, the above feature set may be represented by the 32-bit number0x00 0x00 0x01 0xff, where the 0x prefix indicates that the followingtwo digits are in hexadecimal and where “f” indicates the number 1111 inbinary. In this case, feature descriptors 1 through 9 may be mapped tobits 24 through 32, where 32 is the least significant bit, and no otherfeatures may be activated.

At block 406, in the case of a newly-created license, a determination ismade that the license is bound to the particular component. Thecomponent is verified by comparing the unique ID of the component withthe unique ID in the license. In some embodiments, the manufacturer ofthe component and the type of the component may also be compared with amanufacturer and type of the component specified in the license. In someembodiments, the manufacturer and type may be supplied by the component.In many embodiments, the manufacturer and type may consist of fourfields, the vendor, the device type, the sub vendor, and the sub devicetype. A sub vendor may be a manufacturer which makes a product foranother vendor. In further embodiments, the last two fields may beoptional.

At block 408, the feature set is sent to the component pursuant to theuniform protocol by using a “Feature Enablement” operation. Theoperation may be implemented as a command in a management protocol, suchas NC-SI or MCTP, if the component communicates with a controller underthat management protocol. In some embodiments, data may be sent alongwith a “Feature Enablement” request. A bitmap representing features tobe enabled may, for example, be placed in a buffer to be made availableto the component. In some embodiments, a password, passphrase, or othertoken may also be passed to the component.

At block 410, the component activates the licensed features. Firmware ofthe component may parse the bitmap to determine which features toactivate. The firmware may also verify a password, passphrase, or othersecurity token, if one is included with the “Feature Enablement”command. The firmware may also return the bit map to the license managersubsystem for verification if needed.

In addition to activating licenses, the license manager subsystem maydelete licenses. It may determine whether to delete a license, at block412. If the determination is made, the license manager subsystem mayissue a license revocation command to the component, at block 414. Insome embodiments, implementation of a “Revoke License” command may bemandatory for devices and controllers adhering to the licensingprotocol. If the delete action has been selected, the license file isremoved from the specific component and the license file is unassignedat block 416.

If the delete action has been performed or a delete action was notselected, at block 418 the license manager subsystem determines whetherthere are any other components that may need a license. If so, flowreturns to block 302. Otherwise, the method ends.

As shown in FIG. 5, the information handling system 500 can include afirst physical processor 502 coupled to a first host bus 504 and canfurther include additional processors generally designated as n^(th)physical processor 506 coupled to a second host bus 508. The firstphysical processor 502 can be coupled to a chipset 510 via the firsthost bus 504. Further, the n^(th) physical processor 506 can be coupledto the chipset 510 via the second host bus 508. The chipset 510 cansupport multiple processors and can allow for simultaneous processing ofmultiple processors and support the exchange of information withininformation handling system 500 during multiple processing operations.

According to one aspect, the chipset 510 can be referred to as a memoryhub or a memory controller. For example, the chipset 510 can include anAccelerated Hub Architecture (AHA) that uses a dedicated bus to transferdata between first physical processor 502 and the n^(th) physicalprocessor 506. For example, the chipset 510, including an AHAenabled-chipset, can include a memory controller hub and an input/output(I/O) controller hub. As a memory controller hub, the chipset 510 canfunction to provide access to first physical processor 502 using firstbus 504 and n^(th) physical processor 506 using the second host bus 508.The chipset 510 can also provide a memory interface for accessing memory512 using a memory bus 514. In a particular embodiment, the buses 504,508, and 514 can be individual buses or part of the same bus. Thechipset 510 can also provide bus control and can handle transfersbetween the buses 504, 508, and 514.

According to another aspect, the chipset 510 can be generally consideredan application specific chipset that provides connectivity to variousbuses, and integrates other system functions. For example, the chipset510 can be provided using an Intel® Hub Architecture (IHA) chipset thatcan also include two parts, a Graphics and AGP Memory Controller Hub(GMCH) and an I/O Controller Hub (ICH). For example, an Intel 820E, an815E chipset, or any combination thereof, available from the IntelCorporation of Santa Clara, Calif., can provide at least a portion ofthe chipset 510. The chipset 510 can also be packaged as an applicationspecific integrated circuit (ASIC).

The information handling system 500 can also include a video graphicsinterface 522 that can be coupled to the chipset 510 using a third hostbus 524. In one form, the video graphics interface 522 can be anAccelerated Graphics Port (AGP) interface to display content within avideo display unit 526. Other graphics interfaces may also be used. Thevideo graphics interface 522 can provide a video display output 528 tothe video display unit 526. The video display unit 526 can include oneor more types of video displays such as a flat panel display (FPD) orother type of display device.

The information handling system 500 can also include an I/O interface530 that can be connected via an I/O bus 520 to the chipset 510. The I/Ointerface 530 and I/O bus 520 can include industry standard buses orproprietary buses and respective interfaces or controllers. For example,the I/O bus 520 can also include a Peripheral Component Interconnect(PCI) bus or a high speed PCI-Express bus. In one embodiment, a PCI buscan be operated at approximately 66 MHz and a PCI-Express bus can beoperated at more than one speed, such as 2.5 GHz and 5 GHz. PCI busesand PCI-Express buses can be provided to comply with industry standardsfor connecting and communicating between various PCI-enabled hardwaredevices. Other buses can also be provided in association with, orindependent of, the I/O bus 520 including, but not limited to, industrystandard buses or proprietary buses, such as Industry StandardArchitecture (ISA), Small Computer Serial Interface (SCSI),Inter-Integrated Circuit (I²C), System Packet Interface (SPI), orUniversal Serial buses (USBs).

In an alternate embodiment, the chipset 510 can be a chipset employing aNorthbridge/Southbridge chipset configuration (not illustrated). Forexample, a Northbridge portion of the chipset 510 can communicate withthe first physical processor 502 and can control interaction with thememory 512, the I/O bus 520 that can be operable as a PCI bus, andactivities for the video graphics interface 522. The Northbridge portioncan also communicate with the first physical processor 502 using firstbus 504 and the second bus 508 coupled to the n^(th) physical processor506. The chipset 510 can also include a Southbridge portion (notillustrated) of the chipset 510 and can handle I/O functions of thechipset 510. The Southbridge portion can manage the basic forms of I/Osuch as Universal Serial Bus (USB), serial I/O, audio outputs,Integrated Drive Electronics (IDE), and ISA I/O for the informationhandling system 500.

The information handling system 500 can further include a diskcontroller 532 coupled to the I/O bus 520, and connecting one or moreinternal disk drives such as a hard disk drive (HDD) 534 and an opticaldisk drive (ODD) 536 such as a Read/Write Compact Disk (R/W CD), aRead/Write Digital Video Disk (R/W DVD), a Read/Write mini-Digital VideoDisk (R/W mini-DVD), or other type of optical disk drive.

Although only a few exemplary embodiments have been described in detailherein, those skilled in the art will readily appreciate that manymodifications are possible in the exemplary embodiments withoutmaterially departing from the novel teachings and advantages of theembodiments of the present disclosure. For example, the methodsdescribed in the present disclosure can be stored as instructions in acomputer readable medium to cause a processor, such as chipset 510, toperform the method. Additionally, the methods described in the presentdisclosure can be stored as instructions in a non-transitory computerreadable medium, such as a hard disk drive, a solid state drive, a flashmemory, and the like. Accordingly, all such modifications are intendedto be included within the scope of the embodiments of the presentdisclosure as defined in the following claims. In the claims,means-plus-function clauses are intended to cover the structuresdescribed herein as performing the recited function and not onlystructural equivalents, but also equivalent structures.

What is claimed is:
 1. A system, comprising: a hardware processor, and amemory device accessible to the hardware processor, the memory devicestoring instructions that when executed cause the hardware processor toperform operations including: receiving a peripheral component interfaceidentifier sent via a peripheral component interface from a component;querying an electronic listing for the peripheral component interfaceidentifier, the electronic listing electronically associating licensesand peripheral component interface identifiers including the peripheralcomponent interface identifier sent via the peripheral componentinterface from the component; determining the component lacks a licensein response to the electronic listing lacking an electronic associationwith the peripheral component interface identifier; and requesting thelicense associated with the component.
 2. The system of claim 1, whereinthe operations further comprise commanding the component to send theperipheral component interface identifier.
 3. The system of claim 1,wherein the operations further comprise verifying a manufacturerassociated with the component.
 4. The system of claim 1, wherein theoperations further comprise sending the peripheral component interfaceidentifier to a licensing server.
 5. The system of claim 1, wherein theoperations further comprise receiving the license associated with thecomponent.
 6. The system of claim 1, wherein the operations furthercomprise activating a feature associated with the component.
 7. Thesystem of claim 1, wherein the operations further comprise activatingthe component.
 8. A method, comprising: receiving, by a hardwareprocessor, a peripheral component interface identifier sent via aperipheral component interface from a component; querying, by thehardware processor, an electronic listing for the peripheral componentinterface identifier, the electronic listing electronically associatinglicenses and peripheral component interface identifiers including theperipheral component interface identifier sent via the peripheralcomponent interface from the component; determining, by the hardwareprocessor, the component lacks a license in response to the electroniclisting lacking an electronic association with the peripheral componentinterface identifier; and requesting, by the hardware processor, thelicense associated with the component.
 9. The method of claim 8, furthercomprising commanding the component to send the peripheral componentinterface identifier.
 10. The method of claim 8, further comprisingverifying a manufacturer associated with the component.
 11. The methodof claim 8, further comprising sending the peripheral componentinterface identifier to a licensing server.
 12. The method of claim 8,further comprising receiving the license associated with the component.13. The method of claim 8, further comprising activating a featureassociated with the component.
 14. The method of claim 8, furthercomprising activating the component.
 15. A memory device storinginstructions that when executed cause a hardware processor to performoperations, the operations comprising: receiving a peripheral componentinterface identifier sent via a peripheral component interface from acomponent; querying an electronic listing for the peripheral componentinterface identifier, the electronic listing electronically associatinglicenses and peripheral component interface identifiers including theperipheral component interface identifier sent via the peripheralcomponent interface from the component; determining the component lacksa license in response to the electronic listing lacking an electronicassociation with the peripheral component interface identifier; andrequesting the license associated with the component.
 16. The memorydevice of claim 15, wherein the operations further comprise commandingthe component to send the peripheral component interface identifier. 17.The memory device of claim 15, wherein the operations further compriseverifying a manufacturer associated with the component.
 18. The memorydevice of claim 15, wherein the operations further comprise sending theperipheral component interface identifier to a licensing server.
 19. Thememory device of claim 15, wherein the operations further comprisereceiving the license associated with the component.
 20. The memorydevice of claim 15, wherein the operations further comprise activating afeature associated with the component.